Smart Phone Login Using QR Code

ABSTRACT

Systems and methods are disclosed for a user to use a mobile device such as a smart phone to scan a QR (Quick Response) code displayed on a login webpage of a website. The QR code may encode a server URL of the website. The mobile device decodes the QR code and transmits a device ID and other decoded information to a service provider. The service provider locates login credentials of the user linked to the device ID and communicates the login credentials to a website server for user authentication. Alternatively, the mobile device may transmit its device ID to the website server for the website server to locate a user account linked to the device ID for user login. Alternatively, the mobile device may transmit stored login credentials to the website server. Advantageously, a user may access a website without the need to provide any login credentials.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to and benefit of U.S. ProvisionalPatent Application Ser. No. 61/579,489, filed on Dec. 22, 2011. Thecontent of the provisional application is hereby incorporated byreference in its entirety.

TECHNICAL FIELD

The present disclosure relates generally to systems and methods forauthenticating users over a computer network. In particular, the presentdisclosure relates to methods and systems for efficiently and securelyusing capabilities of mobile devices to facilitate user logins towebpages.

BACKGROUND

Creating and remembering a user name and password for login is oftenchallenging, especially when the user has different user names and/orpasswords for different sites. When a user cannot remember the user nameand/or password when attempting to login to a site, the user may abandona login session or may contact customer support for recovery of thelogin credentials. As a result, companies may encounter reduced loginvolume or may have to expend resources managing user accounts. Often,for ease of remembering the login credentials, a user may use the sameuser name and password for all or most of the user's sites. This is notsecure, as a fraudster who obtains the login credentials for one sitecan then access all the other sites using the same credentials.

Even if the user easily remembers a user name and password, the userstill has to manually enter the information, such as through a keyboardor keypad. This makes the login credentials susceptible to detection bykeylogger spyware or people looking over the user's shoulder, especiallywhen the user is in a public place or attempting to login through apublic computer. While systems have been proposed to more securelyauthenticate users, these systems may require special hardware such asbiometrics readers or near field communication (NFC) devices.Accordingly, it is desirable to provide ways for users to login towebsites conveniently, securely, and efficiently.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a system for a user to use a mobile device to scan QR codedisplayed on a login window to supply identification information to awebsite for the website to authenticate the user according to one ormore embodiments of the present disclosure;

FIG. 2 shows a flow chart of the steps for a user to use a mobile deviceto scan QR code displayed on a login window of a website and to supplydevice ID of the mobile device to the website for the website to linkthe device ID to login credentials of the user according to one or moreembodiments of the present disclosure;

FIG. 3 shows a flow chart of the steps for a website server to receivedevice ID of a mobile device that has scanned QR code displayed on alogin window of a website for the website server to link logincredentials of a user to the mobile device according to one or moreembodiments of the present disclosure;

FIG. 4 shows a flow chart of the steps for a service provider to receivedevice ID of a mobile device that has scanned QR code displayed on alogin window of a website for the service provider to link logincredentials of a user to the device ID and to supply the logincredentials to the website according to one or more embodiments of thepresent disclosure; and

FIG. 5 is a block diagram of a computer system suitable for implementingone or more components discussed herein according to one embodiment ofthe present disclosure.

Embodiments of the present disclosure and their advantages are bestunderstood by referring to the detailed description that follows. Itshould be appreciated that like reference numerals are used to identifylike elements illustrated in one or more of the figures.

DETAILED DESCRIPTION

Systems and methods are disclosed herein for a user to use a mobiledevice such as a smart phone to scan a QR (Quick Response) codedisplayed on a login webpage of a website. The mobile device suppliesidentification information of the mobile device to a server of thewebsite. The server locates login credentials linked to the deviceidentification information to enable the user to login to the websitewithout having to manually enter login credentials. The mobile devicemay also supply identification information of the mobile device to aservice provider that stores multiple login credentials of the user formultiple sites. The service provider locates login credentials of theuser linked to the device identification information for a websiteidentified by the mobile device. The service provider communicates thelogin credentials of the user to a server of the website for the serverto authenticate the user.

The login webpage of the website may display a randomly generated 2D QRcode alongside a login box. The QR code may encode a server URL (UniformResource Locator) for the website, and other information such as asession ID. The user scans the QR code with the mobile device. Themobile device decodes the QR code to obtain the server URL and otherinformation encoded in the QR code. The mobile device may transmit adevice ID of the mobile device and other information such as thelocation information of the mobile device to the server URL. The serververifies that there are login credentials linked to the device ID. Theserver grants the user access to the website based on the linked logincredentials and may perform further authentication using informationreceived from the mobile device. If login credentials are not linked tothe device ID (such as when the user is attempting to login to thewebsite through the QR code for the first time), the server may requestthe user to provide the login credentials for linking with the deviceID. The user may supply the login credentials from the mobile device.The website may verify that the received login credentials match logincredentials the server has on file for the user and may link the mobiledevice to the login credentials. Subsequently, the user may login to thewebsite by simply providing the device ID from the mobile device. In oneor more embodiments, the mobile device may securely store the logincredentials of the user (e.g., a username, password, PIN, or other userauthentication information) for the website. After scanning the QR code,the mobile device may supply the login credentials for the websiteinstead of the device ID to the website. The website may authenticatethe user in the usual manner without the need to store the deviceidentification information.

Advantageously, the user may access a website even if the user forgetsthe login credentials for the site. Security is enhanced because theuser is not required to enter login credentials that may be stolen,seen, or copied. The QR code itself also does not need to contain anyuser account information. The QR code may be a transient bridgeconnecting the mobile device and the website server. Thus, interceptionof the QR code does not expose login credentials or compromise loginsecurity. Scanning a QR code is also easier and faster than typing inuser names and passwords, especially longer user names and passwords.Scanning is preferred by many users who cannot type due to disabilityand who do not like typing like seniors.

In accordance with one or more embodiments of the present disclosure, anapparatus is disclosed. The apparatus includes a network interface thatcommunicates with devices over a network. The apparatus also includes amemory that stores machine-readable instructions. The apparatus furtherincludes one or more processors that execute the machine-readableinstructions to receive a login request for a user from a user device.The login request is received from a scan by the user device of a codedisplayed on a login page of a website. The processors also identifyfrom the login request a user account associated with the website. Theprocessors further cause the user to be granted access to the website.

In accordance with one or more embodiments of the present disclosure, amethod is disclosed. The method includes receiving by a processor of aserver a login request for a user from a user device. The login requestis received from a scan by the user device of a code displayed on alogin page of a website. The method further includes identifying fromthe login request a user account associated with the website. The methodfurther includes granting the user access to the website.

In accordance with one or more embodiments of the present disclosure, anon-transitory computer readable medium having computer readable codefor execution by a processor of a server to perform a method isdisclosed. The method includes receiving a login request for a user froma user device. The login request is received from a scan by the userdevice of a code displayed on a login page of a website. The methodfurther includes identifying from the login request a user accountassociated with the website. The method further includes causing theuser to be granted access to the website.

Refer now to the figures wherein the drawings are for purposes ofillustrating embodiments of the present disclosure only, and not forpurposes of limiting the same. FIG. 1 shows a system for a user to use amobile device to scan QR code displayed on a login window to supplyidentification information to a website for the website to authenticatethe user according to one or more embodiments of the present disclosure.

A user 100 carries a mobile device 102. Mobile device 102 may be a smartphone (e.g., iPhone, Google phone, or other phones running Android,Window Mobile, or other operating systems), a tablet computer (e.g.,iPad, Galaxy), personal digital assistant (PDA), a notebook computer, orvarious other types of wireless or wired computing devices. It should beappreciated that mobile device 102 may be referred to as a client deviceor a customer device without departing from the scope of the presentdisclosure. Mobile device may have a camera. Mobile device 102 maycommunicate over a network 106 with a service provider 116 or with awebsite server 108. In one embodiment, service provider 116 may act asan intermediary between mobile device 102 and website server 108 tofacilitate user authentication by website server 108.

Network 106 may be implemented as a single network or a combination ofmultiple networks. For example, in various embodiments, network 106 mayinclude the Internet and/or one or more intranets, wireless networks(e.g., cellular, wide area network (WAN), WiFi hot spot, WiMax, personalarea network (PAN), Bluetooth, etc.), landline networks and/or otherappropriate types of communication networks. As such, in variousembodiments, mobile device 102 may be associated with a particular link(e.g., a link, such as a URL (Uniform Resource Locator) to an IP(Internet Protocol) address).

In one or more embodiments, user 100 is at a PC 104 and wishes to accessa website running on website server 108. User 100 may enter a URLaddress of the website or may click on a link to the website. Websiteserver 108 displays a login window of a webpage on a screen of PC 104requesting the user to provide login credentials such as a user name anda password. The login webpage also displays a 2D QR code. The QR codemay encode a URL of website server 108 and other information presentedby the website server 108, such as a merchant ID, a session ID, atransaction ID, etc. While the exemplary embodiments described hereinshows QR code on a login webpage displayed on a screen of PC 104, othersymbols or data encoding schemes, such as UPC code, may also bedisplayed. Similarly, the login webpage may be displayed on a TV, kiosk,tablet computer, notebook computer, mobile device, or other types ofscreen terminals or display medium. Furthermore, the information encodedmay be used to facilitate other types of human machine interface, notjust for logging into a website. User 100 uses the camera on mobiledevice 102 to scan the QR code of the login webpage displayed on thescreen of PC 104. User 100 may scan the QR code by opening a mobile appof the website or of service provider 116 to activate the camera. Mobiledevice 102 may contain QR code reading software to capture and decodethe captured QR code. The decoded URL and other decoded information suchas the session ID, merchant ID, transaction ID, etc. may be received bythe mobile app. The mobile app may inform mobile device 102 that logincredentials are requested.

Mobile device 102 may transmit an encrypted device ID, the session ID,and other decoded information to the URL of website server 108 throughnetwork 106 if the mobile app used to scan the QR code is from thewebsite running on website server 108. Alternatively, mobile device 102may transmit the encrypted device ID, the URL of the website hosted onwebsite server 108, the merchant ID, and other decoded information tothe service provider 116 through network 106 if the mobile app is fromthe service provider 116. Website server 108 may have a networkinterface 110 that interfaces with network 106 to receive the device IDof mobile device 102. Website server 108 may invoke a userauthentication unit 112 to verify if the device ID is linked to a useraccount. An account has been linked to the device ID if user 100 haspreviously logged into the website by scanning the QR code using mobiledevice 102 or if user 100 has otherwise logged into the website frommobile device 102. If an account is linked with the device ID, websiteserver 108 may retrieve account information linked to the device ID,including user login credentials, from an account database 114. Websiteserver 108 may grant user 100 access to the website and may present ascreen on mobile device 102 confirming that user 100 is logged in to thewebsite.

If the device ID is not linked with a user account, then user 100 may beattempting to login to website server 108 using the scanned QR code frommobile device 102 for the first time. Website server 108 may requestuser 100 to provide login credentials from the mobile device 102 bypresenting a login screen on mobile device 102. User 100 may enter auser name and password (or other information as required by websiteserver 108), such as an e-mail address and a PIN for the logincredentials. User 100 may enter the requested information on mobiledevice 102 through a keyboard, keypad, touchscreen, or voice command.Mobile device 102 transmits the login credentials to website server 108,where user authentication unit 112 processes the login credentials inthe same way it would if user 100 entered the login credentials manuallythrough a login window. If the login credentials provided by user 100match the login credentials website server 108 has in account database114, user 100 is authenticated. Website server 108 may link the deviceID to the login credentials and grants user 100 access to the website.Website server 108 may present a screen on mobile device 102 confirmingthat user 100 is logged in and that the device ID has been linked to thelogin credentials. If the login credentials provided by user 100 do notmatch the login credentials website server 108 has in account database114, website server 108 may request user 100 to re-enter the logincredentials until user 100 is successfully authenticated or until athreshold number of unsuccessful login attempts is reached.Alternatively, if user 100 does not have an established account withwebsite server 108, user 100 may be requested to register as a newaccount holder using the provided login credentials.

In one embodiment, mobile device 102 may store the login credentials.For example, the mobile app for the website may store the logincredentials of user 100 for the website. The stored login credentialsmay be provided as a convenience to user 100 if user 100 needs to bereminded of the login credentials when attempting to login to websiteserver 108 from another device. Mobile device 102 may also transmit thestored login credentials to website server 108 or service provider 116to request user access to the website without relying on the device ID.Thus, website server 108 may not need to store device IDs or to link adevice ID to the login credentials of user 100, allowing authenticationof user 100 to be performed in the usual manner.

In one embodiment, service provider 116 may act as an intermediarybetween mobile device 102 and website server 108. Service provider 116may store the login credentials linked to the device ID for a multitudeof website in a login credentials database 122. User 100 who wishes tologin to a website may open a mobile app of service provider 116 to scanthe QR code displayed on a login webpage of the website. As before, codereading software on mobile device 102 may capture and decode the QR codeto yield the URL of the website and other decoded information. Mobiledevice 102 may transmit an encrypted device ID, the URL of the website,a session ID, and other decoded information to service provider 116through network 106. Service provider 116 may have a network interface118 that interfaces with network 106 to receive the transmission frommobile device 102. Service provider 116 may invoke a login credentialsverification unit 120 to verify if the received device ID is linked toan account of the website identified by the received URL. If an accountfor the website is linked with the device ID, service provider 116 mayretrieve the login credentials of the account from login credentialsdatabase 122. Service provider 116 may transmit the login credentials tothe URL of website server 108 for authentication. Website server 108 mayinvoke user authentication unit 112 to authenticate the logincredentials. After user 100 is authenticated, website server 108 maygrant user 100 access to the website and may present a loginconfirmation screen on mobile device 102.

If the received ID is not linked with an account of the websiteidentified by the URL, user 100 is attempting to login to the websiteusing the scanned QR code from mobile device 102 for the first time.Service provider 116 may request user 100 to provide login credentialsfrom mobile device 102 by presenting a login screen on mobile device102. As when website server 108 requests user 100 to provide logincredentials for linking with the device ID, user 100 may enter a username and password on mobile device 102 for the login credentials. Mobiledevice 102 transmits the login credentials to service provider 116,which may store the login credentials as account information for thewebsite. Service provider 116 may link the device ID to the logincredentials for the website identified by the URL. Service provider 116may transmit the login credentials to the URL of website server 108 forauthentication through network 106. If authentication is successful,website server 108 may grant user 100 access to the website. Websiteserver 108 may, directly or through service provider 116, present ascreen on mobile device 102 confirming that user 100 is logged in andthat the device ID has been linked to the login credentials.

If the login credentials cannot be authenticated, website server 108,directly or through service provider 116, may request user 100 tore-enter the login credentials. When user 100 re-enters the logincredentials, service provider 116 may store the login credentials, linkthe login credentials to the device ID, and transmit the logincredentials to website server 108 for authentication. If the user 100has not established account with the website identified by the URL, user100 may be requested to register as a new account holder using theprovided login credentials. In one embodiment, the mobile app for theservice provider 116 may store the login credentials on mobile device109 if user 100 ever needs to be reminded of the login credentials forthe website.

FIG. 2 shows a flow chart of the steps for a user to use a mobile deviceto scan QR code displayed on a login window of a website and to supplydevice ID of the mobile device to the website server of FIG. 1 for thewebsite server to link the device ID to login credentials of the useraccording to one or more embodiments of the present disclosure. In step202, user 100 opens an application, such as a mobile app of websiteserver 108 on mobile device 102. The application may direct user 100 toscan a QR code displayed on the login webpage of a website hosted onwebsite server 108. The login webpage may be displayed on a screen of aPC 104. In step 204, user 100 uses a camera on mobile device 102 tocapture the QR code. The QR code may encode a URL of the website andother information such as a merchant ID, a randomly generated sessionID, a transaction ID, etc. Code reading software may decode the QR codefor the application. The application may inform mobile device 102 thatlogin credentials to the website URL are requested.

In step 206, mobile device 102 transmits an encrypted device ID ofmobile device 102 to website server 108 designated by the decoded URL.Mobile device 102 may also transmit to website server 108 informationdecoded from the QR code, such as the session ID, and/or informationgenerated by mobile device 102, such as its GPS location. Website server108 receives the transmission and determines if the device ID is linkedto a user account. An account may be linked to the device ID if user 100has previously logged into the website from mobile device 102 using theQR code or through other ways. If an account is linked to the device ID,website server 108 may login the user and may retrieve information onthe user account. Website server 108 may transmit a login confirmationpage to mobile device 102. In step 208, mobile device 102 determines ifthe login confirmation page is received. If it is, user may proceed toaccess the website in step 220.

In one embodiment, mobile device 102 may have stored the logincredentials for the website URL when user 101 previously entered thelogin credentials into mobile device 102. When the application informsmobile device 102 that login credentials to the website URL arerequested, mobile device 102 may determine that it has the logincredentials. In step 206, mobile device 102 may transmit the logincredentials to website server 108 in place of, or in addition to, theencrypted device ID of mobile device 102. Website server 108 mayauthenticate user 100 using the received login credentials and maygenerate a login confirmation page to mobile device 102 when user 100 isgranted access to the website. Thus, the determination of whether thedevice ID is linked to a user account may be made at mobile device 102as well at website server 108.

If website server 108 determines that the device ID is not linked to auser account, website server 108 presents a login screen on mobiledevice 102 requesting user 100 to provide login credentials. The loginscreen may also allow user 100 to create an account if user 100 does nothave an account with website server 108. In step 210, a decision is madeon whether user 100 has an account with website server 108. If user 100has an account, user 100 enters the login credentials into mobile device102 in step 212. User 100 may enter a user name and a password using akeyboard, keypad, touchscreen, voice command, or through other methodsof user input. Mobile device 102 may transmit the login credentials towebsite server 108 for authentication of user 100. If website server 108is able to authenticate user 100 with the login credentials, websiteserver 108 may link the device ID to the login credentials so that user100 may initiate future login requests from mobile device 102 bytransmitting the device ID. Website server 108 may generate a loginconfirmation page to mobile device 102 to grant user 100 access to thewebsite. In step 214, mobile device 102 determines if the loginconfirmation page is received. If it is, user authentication issuccessful and the application stores the login credentials for thewebsite URL in step 216. User 100 may proceed to access the website. Inone embodiment, the application may not store the login credentials. Ifwebsite server 108 cannot authenticate user 100 because the logincredentials are wrong, mobile device 102 does not receive the loginconfirmation page from website server 108 in step 214. User may berequested to re-enter the login credentials until user 100 isauthenticated or until a threshold number of unsuccessful login attemptsis reached.

If user 100 does not have an account with website server 108, user 100would need to create an account. In step 218, user 100 creates anaccount by entering a user name, password, and other informationrequested on the login screen into mobile device 102. Again, user 100may enter the information using a keyboard, keypad, touchscreen, voicecommand, or through other methods of user input. Website server 108 maystore the received account information, link the device ID to the logincredentials, and generate a new account confirmation page to mobiledevice 102. In step 216, when mobile device receives the new accountconfirmation page, the application stores the login credentials for thewebsite URL. User 100 may proceed to access the website. In oneembodiment, the application may not store the login credentials. Thus,user 100 may login to website server 108 by using the device ID ofmobile device 102 that is linked to a user account, by entering thelogin credentials of an established account for linking with the deviceID, or by creating login credentials for a new account for linking withthe device ID.

FIG. 3 shows a flow chart of the steps for a website server to receivedevice ID of a mobile device that has scanned QR code displayed on alogin window of a website of FIG. 1 for the website server to link logincredentials of a user to the mobile device according to one or moreembodiments of the present disclosure. In step 302, website server 108presents QR code on a login webpage of the website hosted on websiteserver 108. The login webpage may be displayed on a screen of a PC 104or other types of terminals. The QR code may encode a URL of the websiteand other information such as a merchant ID, a randomly generatedsession ID, a transaction ID, etc. User 100 uses a camera on mobiledevice 102 to capture the QR code and invokes code reading software todecode the QR code to obtain the website URL and other information.

In step 304, website server 108 receives an encrypted ID of mobiledevice 102 from mobile device 102. Website server 108 may also receivefrom mobile device 102 information decoded from the QR code, such as asession ID, and/or information on the mobile device 102, such as its GPSlocation. In step 306, website server 206 determines if the receiveddevice ID is linked to a user account. If it is, website server 108 mayretrieve account information of the user account. In step 320, websiteserver 108 logins user 100 to grant user 100 access to the website.Website 108 may transmit a login confirmation page to mobile device 102.

If website server 108 determines that the device ID is not linked to anyuser account, website server presents a login screen on mobile device102 requesting user 100 to provide login credentials in step 308. Thelogin screen may also request user 100 to create an account if user 100does not have an account with the website. In step 310, user 100 decidesif user 100 has an account with the website. If user 100 has an account,user may enter the login credentials, such as a user name and apassword, into mobile device 102. In step 312, website server 108receives the login credentials from mobile device 102. In step 314,website server 108 attempts to login user 100 using the received logincredentials. If website server 108 is able to authenticate user 100using the login credentials, in step 316 website server 108 links thedevice ID to the login credentials so that user 100 may be logged intothe website in the future by transmitting the device ID from mobiledevice 102. In step 320, website server 108 logins user 100 into thewebsite. Website 108 may transmit a login confirmation page to mobiledevice 102. If website server 108 is not able to authenticate user 100using the received login credentials, website server 108 may display amessage on the login screen of mobile device 102 informing user 100 thatthe login credentials are wrong. User 100 may re-enter the logincredentials until user 100 is authenticated or until a threshold numberof unsuccessful login attempts is reached.

If user does not have an account, user 100 may select an option on thelogin screen to create a new account. User 100 may create logincredentials such as a user name, password, and may enter otherinformation into mobile device 102. In step 318, website server 108receives the login credentials from mobile device 102 to create a newaccount for user 100. In step 316, website server 108 links the deviceID to the login credentials for the new account. In step 320, websiteserver 108 logins user 100 into the website. Website 108 may transmit anew account confirmation page to mobile device 102 informing user 100that a user account has been created for the website and that the logincredentials have been linked to the device ID of mobile device 102.Thus, website server 108 may authenticate user 100 by using the deviceID of mobile device 102 that is linked to a user account, by receivinglogin credentials of an established account to link with the device ID,or by receiving login credentials for a new account to link with thedevice ID.

FIG. 4 shows a flow chart of the steps for a service provider to receivedevice ID of a mobile device that has scanned QR code displayed on alogin window of a website of FIG. 1 for the service provider to linklogin credentials of a user to the device ID and to supply the logincredentials to the website according to one or more embodiments of thepresent disclosure. Service provider 116 may act as an intermediarybetween mobile device 102 and a multitude of websites by storing thelogin credentials linked to mobile device 102 for the websites. In step402, website server 108 presents, on a screen of a PC 104, QR code of alogin window of a website hosted on website server 108. User 100 uses acamera on mobile device 102 to capture the QR code. Mobile device 102may invoke code reading software to decode the QR code to obtain thewebsite URL and other information encoded by the QR code.

In step 404, service provider 116 receives from mobile device 102 anencrypted device ID of mobile device 102, the website URL, and otherdecoded information such as a session ID from mobile device 102. In step406, service provider 116 determines if the received device ID is linkedwith a user account for the website URL. If it is, service provider 116retrieves the login credentials of the user account and transmits thelogin credentials to website server 108 for authentication in step 414.If website server 108 is able to authenticate user 100 using the logincredentials, website server 108 may transmit a login confirmation pageto mobile device 102. In one embodiment, website server 108 may requestservice provider 116 to transmit a login confirmation page to mobiledevice 102.

If the received device ID is not linked with an account for the websiteURL, service provider 116 presents a login screen on mobile device 102requesting user 100 to provide login credentials for the website in step408. The login screen may also request user 100 to create an account ifuser 100 does not have an account with the website. If user 100 has anaccount with the website, user 100 may enter login credentials such as auser name and password into mobile device 102. In step 410, serviceprovider 116 receives the login credentials from mobile device 102. Instep 412, service provider 116 links the device ID to the logincredentials for the website. In step 414, service provider 116 transmitsthe login credentials to website server 108 for authentication. Ifauthentication is successful, service provider 116 may transmit a loginconfirmation page to mobile device 102 confirming that user 100 islogged in and that the device ID has been linked to the logincredentials. If authentication fails, service provider 116 may display amessage on the login screen of mobile device 102 informing user 100 thatthe login credentials are wrong. User 100 may re-enter the logincredential. Service provider 116 may receive the new login credentialsfrom mobile device 102, link the device ID to the new login credentials,and transmit the new login credentials to website server 108 forauthentication. In one embodiment, user 100 may be prevented fromlogging in if service provider 116 detects a threshold number ofunsuccessful login attempts from mobile device 102.

In one or more embodiments, if user does not have an account with thewebsite, user 100 may select an option on the login screen to create anew account. User 100 may create login credentials and may enter otherinformation required for creating a new account into mobile device 102.Service provider 116 may receive the login credentials and may link thedevice ID to the new login credentials. Service 116 may transmit thelogin credentials and the other new account information to websiteserver 108 for website server 108 to create a new account for user 100.After the new user account is created by website server 108, serviceprovider 116 may transmit a new account confirmation page to mobiledevice 102 informing user 100 that a user account has been created forthe website, that the device ID has been linked to the logincredentials, and that user 100 has been granted access to the website.

FIG. 5 is a block diagram of a computer system 500 suitable forimplementing one or more embodiments of the present disclosure. Invarious implementations, the mobile device of the user may comprise apersonal computing device (e.g., smart phone, a computing tablet, apersonal computer, laptop, PDA, Bluetooth device, key FOB, badge, etc.)capable of communicating with the network. The website server or theservice provider may utilize a network computing device (e.g., a networkserver) capable of communicating with the network. It should also beappreciated that the mobile app on the mobile device, the process toverify that device ID of a mobile device is linked with a user account,or other user authentication process may be implemented as applicationsrunning on computer system 500.

Network computing device may comprise or implement a plurality ofservers and/or software components that operate to perform variousmethodologies in accordance with the described embodiments. Exemplaryservers may include, for example, stand-alone and enterprise-classservers operating a server OS such as a MICROSOFT® OS, a UNIX® OS, aLINUX® OS, or other suitable server-based OS. It can be appreciated thatthe servers illustrated in FIG. 5 may be deployed in other ways and thatthe operations performed and/or the services provided by such serversmay be combined or separated for a given implementation and may beperformed by a greater number or fewer number of servers. One or moreservers may be operated and/or maintained by the same or differententities.

Computer system 500 includes a bus 502 or other communication mechanismfor communicating information data, signals, and information betweenvarious components of computer system 500. Components include aninput/output (I/O) component 504 that processes a user action, such asselecting keys from a keypad/keyboard, selecting one or more buttons orlinks, etc., and sends a corresponding signal to bus 502. I/O component504 may also include an output component such as a display 511, and aninput control such as a cursor control 513 (such as a keyboard, keypad,mouse, etc.). An optional audio input/output component 505 may also beincluded to allow a user to use voice for inputting information byconverting audio signals into information signals. Audio I/O component505 may allow the user to hear audio. A transceiver or network interface506 transmits and receives signals between computer system 500 and otherdevices, such as another user device, a seller server, or a paymentprovider server via a communication link 518 to a network. In oneembodiment, the transmission is wireless, although other transmissionmediums and methods may also be suitable. A processor 512, which can bea micro-controller, digital signal processor (DSP), or other processingcomponent, processes these various signals, such as for display oncomputer system 500 or transmission to other devices via communicationlink 518. Processor 512 may also control transmission of information,such as cookies or IP addresses, to other devices.

Components of computer system 500 also include a system memory component514 (e.g., RAM), a static storage component 516 (e.g., ROM), and/or adisk drive 517. Computer system 500 performs specific operations byprocessor 512 and other components by executing one or more sequences ofinstructions contained in system memory component 514. Logic may beencoded in a computer readable medium, which may refer to any mediumthat participates in providing instructions to processor 512 forexecution. Such a medium may take many forms, including but not limitedto, non-volatile media, volatile media, and transmission media. Invarious implementations, non-volatile media includes optical, ormagnetic disks, or solid-state drives, volatile media includes dynamicmemory, such as system memory component 514, and transmission mediaincludes coaxial cables, copper wire, and fiber optics, including wiresthat comprise bus 502. In one embodiment, the logic is encoded innon-transitory computer readable medium. In one example, transmissionmedia may take the form of acoustic or light waves, such as thosegenerated during radio wave, optical, and infrared data communications.

Some common forms of computer readable media includes, for example,floppy disk, flexible disk, hard disk, magnetic tape, any other magneticmedium, CD-ROM, any other optical medium, punch cards, paper tape, anyother physical medium with patterns of holes, RAM, PROM, EEPROM,FLASH-EEPROM, any other memory chip or cartridge, or any other mediumfrom which a computer is adapted to read.

In various embodiments of the present disclosure, execution ofinstruction sequences to practice the present disclosure may beperformed by computer system 500. In various other embodiments of thepresent disclosure, a plurality of computer systems 500 coupled bycommunication link 518 to the network (e.g., such as a LAN, WLAN, PTSN,and/or various other wired or wireless networks, includingtelecommunications, mobile, and cellular phone networks) may performinstruction sequences to practice the present disclosure in coordinationwith one another.

Where applicable, various embodiments provided by the present disclosuremay be implemented using hardware, software, or combinations of hardwareand software. Also where applicable, the various hardware componentsand/or software components set forth herein may be combined intocomposite components comprising software, hardware, and/or both withoutdeparting from the spirit of the present disclosure. Where applicable,the various hardware components and/or software components set forthherein may be separated into sub-components comprising software,hardware, or both without departing from the spirit of the presentdisclosure. In addition, where applicable, it is contemplated thatsoftware components may be implemented as hardware components, andvice-versa.

Application software in accordance with the present disclosure, such ascomputer programs executed by a processor of the service provider or thewebsite server to link device ID of a mobile device to a user account,or the mobile app executed by the mobile device to receive the decodedQR code, may be stored on one or more computer readable mediums. It isalso contemplated that the application software identified herein may beimplemented using one or more general purpose or specific purposecomputers and/or computer systems, networked and/or otherwise. Whereapplicable, the ordering of various steps described herein may bechanged, combined into composite steps, and/or separated into sub-stepsto provide features described herein.

Although embodiments of the present disclosure have been described,these embodiments illustrate but do not limit the disclosure. Forexample, even though QR code is a mature technology with largeinformation storage capacity, other code, symbols, text, objects thatmay be recognized quickly and accurately by mobile devices may be usedto convey the information for the login webpage. For example, UPC codecan be used to encode the server URL and a transient session number,which then can be scanned by the mobile device to connect the mobiledevice with the website server to accomplish the novel login process asdiscussed herein. It should also be understood that embodiments of thepresent disclosure should not be limited to these embodiments but thatnumerous modifications and variations may be made by one of ordinaryskill in the art in accordance with the principles of the presentdisclosure and be included within the spirit and scope of the presentdisclosure as hereinafter claimed.

We claim:
 1. An apparatus comprising: a network interface configured tocommunicate with devices over a network; a memory configured to store aplurality of machine-readable instructions; one or more processorsconfigured to execute the machine-readable instructions to: receive alogin request from a user through a user device, wherein the loginrequest is received from a scan of a code on a login page of a website;identify from the login request an account of the user associated withthe website; and cause the user to be granted access to the website. 2.The apparatus of claim 1, wherein the code comprises a server URL forthe website.
 3. The apparatus of claim 1, wherein the login requestcomprises information encoded in the code and an ID of the user device.4. The apparatus of claim 3, wherein to identify from the login requestan account of the user includes to verify that the ID of the user deviceis linked with an account of the user associated with the website. 5.The apparatus of claim 3, wherein to identify from the login request anaccount of the user includes to determine login credentials for anaccount associated with the website linked with the ID of the userdevice, and wherein to cause the user to be granted access to thewebsite includes to communicate the login credentials to the website,wherein the user is granted access to the website if the user isauthenticated using the login credentials.
 6. The apparatus of claim 5,wherein the apparatus stores login credentials for accounts linked tothe user device for a plurality of websites.
 7. The apparatus of claim1, wherein if an account of the user cannot be identified from the loginrequest, the processors are further configured to: transmit a requestfor login credentials to the user device; receive the login credentialsfor the website from the user device; and link the login credentials forthe website to the user device.
 8. The apparatus of claim 1, wherein thelogin request comprises login credentials of the user.
 9. The apparatusof claim 1, wherein the login request is received when the user scansthe code after opening a mobile app on the user device.
 10. Theapparatus of claim 1, wherein the code is a 2D QR code.
 11. A methodcomprising: receiving by a processor of a server a login request from auser through a user device, wherein the login request is received from ascan of a code on a login page of a website; identifying from the loginrequest an account of the user associated with the website; and grantingthe user access to the website.
 12. The method of claim 11, wherein thecode comprises a server URL for the website.
 13. The method of claim 11,wherein the login request comprises information encoded in the code andan ID of the user device.
 14. The method of claim 13, wherein saididentifying from the login request an account of the user comprisesverifying that the ID of the user device is linked with an account ofthe user associated with the website.
 15. The method of claim 13,wherein said identifying from the login request an account of the usercomprises determining login credentials for an account associated withthe website linked with the ID of the user device, and wherein saidgranting the user access to the website comprises communicating thelogin credentials to the website, wherein the user is granted access tothe website if the user is authenticated using the login credentials.16. The method of claim 15, further comprising storing login credentialsfor accounts linked to the user device for a plurality of websites. 17.The method of claim 11, if said identifying fails to identify from thelogin request an account of the user associated with the website,further comprising: transmitting a request for login credentials to theuser device; receiving the login credentials for the website from theuser device; and linking the login credentials for the website to theuser device.
 18. The method of claim 11, wherein the login requestcomprises login credentials of the user.
 19. The method of claim 11,wherein the code is a 2D QR code.
 20. A non-transitory computer readablemedium having computer readable code for instructing a processor of aserver to perform a method, the method comprising: receiving a loginrequest from a user through a user device, wherein the login request isreceived from a scan of a code on a login page of a website; identifyingfrom the login request an account of the user associated with thewebsite; and causing the user to be granted access to the website.